Skip to content

Comments

Add github actions for building and releasing hoist-core to maven central#507

Open
jskupsik wants to merge 9 commits intodevelopfrom
mavenCentral
Open

Add github actions for building and releasing hoist-core to maven central#507
jskupsik wants to merge 9 commits intodevelopfrom
mavenCentral

Conversation

@jskupsik
Copy link
Contributor

No description provided.

# Configure Gradle for optimal use in GiHub Actions, including caching of downloaded dependencies.
# See: https://github.com/gradle/actions/blob/main/setup-gradle/README.md
- name: Setup Gradle
uses: gradle/actions/setup-gradle@417ae3ccd767c252f5661f1ace9f835f9654f2b5 # v3.1.0
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I can tell, we appear to have copied this exact-hash-build-version syntax from the testing suite of the gradle plugin deployment. In their actual release code as well as in every guide I can find, it seems to be recommended to use the version tag.

XH_RELEASE_VERSION: ${{ inputs.xhReleaseVersion }}
run: |
echo $SECRING_FILE | base64 -d > secring.gpg
(set -x; ./gradlew -Psigning.secretKeyRingFile="${GITHUB_WORKSPACE}/secring.gpg" -PxhReleaseVersion="$XH_RELEASE_VERSION" publishToSonatype closeSonatypeStagingRepository --no-daemon)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When done demoing - replace closeSonatypeStagingRepository with closeAndReleaseSonatypeStagingRepository to automatically make it go live

@amcclain
Copy link
Member

@jskupsik what's up with this failing check on this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants